refactor(upgrade): use sets and set lists #1557
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
The failing tests seem to be unrelated. |
brendt
reviewed
Sep 17, 2025
brendt
reviewed
Sep 17, 2025
Contributor
Author
|
Gotta be |
Member
|
Lol, look at me, trying to fix code on GitHub without trying it out >< |
Member
|
Thanks for the PR though, really good! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let the end-users use nice, self-explaining constants instead of verbose strings for sets.
This also adds the possibility to have upgrade sets in the future, eg. from
2.0to2.1,2.1to2.2, etc.Is this something we'd be interested in?